This version of the profile maker contains bug fixes and some enhancements.
ProfileMaker requires System 7.0 or greater.
Below are the known bugs that existed in the previous version of ProfileMaker that have been fixed in the current version:
1. When you opened the data fork of a profile created before, a byte of value $00 was automatically added into the additional data field, and custom data of the profile would be lost.
2. Custom Data offset was set to the end of the profile rather than to where the custom data actually started.
3. When you created a new profile, the size, profileNameOffset and customDataOffset popUp buttons were set to "AutoCalc" causing the value of these fields to be calculated automatically. However, if you loaded an existing profile from a file, the pop up menu items of these fields were set to the data read from the profile. Now when you load a profile, the pop up menu items to set the size, profileNameOffset, and customDataOffset are set to "AutoCalc".
4. Using the pop up menu item to set a profile field whose type was OSType would cause the system to crash. This was discovered after the previous Profile Maker version was released. This is now fixed.
5. If you loaded a profile that contained n response elements, and then loaded a profile that contained m response elements, with m being less than n, the first m response elements would be loaded, but the rest of the response elements would not be cleared.
The following behavior is a feature and not a bug:
1. If the profile name size (including the length byte) is odd, a $00 byte is appended to that the custom data starts on a word boundary.
Enhancements:
A new feature has been added to the profile maker that allows the user to read in TRC curve data directly from the text file.
The format of the text file must be as follows:
The first entry must be the device type.
The device type may be 'Monitor' or 'Printer'. The program is not case sensitive.
Following the device type the colorants must be entered. There must be at least one whitespace such as a tab or a <CR> following the device type and following each colorant.
If the device type is Monitor, the program will expect the X Y and Z colorant values for Red, Green, and Blue.
If the device type is Printer, the program will expect the X Y and Z colorant values for White, Black, Red, Green, Blue, Cyan, Magenta, and Yellow in that order.
Following the colorant values the user should specify the number of entries in the TRC table. The number of entries count must be tab separated from the last colorant value.
The program assumes that if device type is Monitor, that TRC data will be entered for Red, Green and Blue; and if the device type is Printer, that TRC data will be entered for Black, Cyan Magenta and Yellow.
Important:
After the last TRC entry has been entered in the text file, there must be a white space character.
The following is an example text file. The <CR> represents a physical <CR> the user must add.
